<html><!-- Copyright (C) 2007 Laurent A.V. Szyster - Copylef GPL 2.0 -->
<head>
  <title>protocols.js</title>
  <link href="site.css" type="text/css" rel="stylesheet"></link>
  <link href="protocols.css" type="text/css" rel="stylesheet"></link>
</head>
<body>
<div>  
  <h1><a href="/">protocols.js</a></h1>
  <div class="menu">
    <a href="documentation.html">Documentation</a>
    <a href="licence.html">Licence</a>
    <a href="http://code.google.com/p/protocols/source">Sources</a>
  </div>
  <p>
    If the network is the computer then protocols are its application 
    programming interfaces.
  </p>
  <p>
    Great JavaScript applications of HTTP, HTML, CSS and JSON are written
    as a web of URLs, hypertext markup, cascading styles and JavaScript
    object notations. 
  </p>
  <p>
    Protocols is a small library of JavaScript conveniences to apply
    the stable stack of web protocols for common browsers, with less code
    and more lever on protocols.
  </p>
  <p>
    It combines the pearls of blog wisdom, some bits of Crockford's sagacity,
    a great deal of Jock Slocum's selector and two cents of Prototype's tips.
  </p>
  <p>
    Its sources are kept small by avoiding the temptation of yet another GUI
    library in a browser.
  </p>
  <p>
    Web protocols are meant to decouple visual design (CSS) from the page 
    flows (HTML), the interactivity automations (JavaScript), the network 
    resource controllers (HTTP) and the application's object models (JSON).
  </p>
  <p>
    I won't bring back the fat GUI client zombies back from the 80's.
  </p>
</div>
</body>
</html>